Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1182

reference: 917-tree-1
name: 1182
tree-preservation-order: undefined
917-tpo-1
uprn
address-text
point: POINT (-1.031060 50.867231)
geometry: MULTIPOLYGON (((-1.030947 50.867219,-1.030952 50.867241,-1.030967 50.867261,-1.030992 50.867277,-1.031024 50.867288,-1.031059 50.867292,-1.031094 50.867288,-1.031126 50.867279,-1.031151 50.867263,-1.031168 50.867243,-1.031174 50.867221,-1.031169 50.867198,-1.031153 50.867178,-1.031128 50.867162,-1.031097 50.867152,-1.031062 50.867148,-1.031026 50.867151,-1.030995 50.867161,-1.030969 50.867177,-1.030953 50.867197,-1.030947 50.867219)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL